Repository navigation
Conversation
Contributor
CI report —
|
| Workflow | Result | Time | Run |
|---|---|---|---|
| CI | ✅ success | 0m18s | #13 |
| Docs | ✅ success | 0m28s | #87 |
Docs
Doxygen warnings
0 warning(s) in the files this pull request changes, which fail the check; 48 more elsewhere, which do not. The full list is in the job log and the doxygen-warnings artifact of the Docs workflow.
Gaps in files this pull request does not change, by file:
| Warnings | File |
|---|---|
| 17 | include/libe3/logger.hpp |
| 9 | include/libe3/dapp_subscription_state.hpp |
| 7 | include/libe3/lockfree_queue.hpp |
| 6 | include/libe3/mpmc_queue.hpp |
| 1 | include/libe3/error_codes.h |
| 1 | include/libe3/libe3.hpp |
| 1 | src/connector/zmq_connector.hpp |
Ready to merge (fast-forward only)
A maintainer can land the reviewed commits with:
git fetch origin
git checkout main && git merge --ff-only f6021c0cc4dae017452c7e962dec75a484f1e6dd && git push origin mainHead: f6021c0cc4dae017452c7e962dec75a484f1e6dd (branch docs/85-115-positions). If --ff-only fails as non-fast-forward, the branch must be rebased on the latest main.
One comment per PR, rewritten in place once every workflow for
f6021c0finished.
This was referenced Nov 7, 2026
Thecave3
force-pushed
the
docs/111-control-answer
branch
from
November 7, 2026 15:09
fdd28fb to
814f8dd
Compare
Thecave3
force-pushed
the
docs/85-115-positions
branch
from
November 7, 2026 15:09
32bb9e8 to
5367e2d
Compare
This was referenced Nov 9, 2026
Thecave3
force-pushed
the
docs/85-115-positions
branch
from
November 9, 2026 22:44
5367e2d to
51c8afb
Compare
Thecave3
force-pushed
the
docs/111-control-answer
branch
from
November 10, 2026 12:41
f510015 to
8ad45dd
Compare
Thecave3
force-pushed
the
docs/85-115-positions
branch
from
November 10, 2026 12:41
51c8afb to
a997f39
Compare
Thecave3
force-pushed
the
docs/111-control-answer
branch
from
November 11, 2026 01:44
8ad45dd to
36f90d4
Compare
Thecave3
force-pushed
the
docs/85-115-positions
branch
from
November 11, 2026 01:44
a997f39 to
e86c612
Compare
… can be proposed A libe3 RAN agent serves one link and one encoding, set in its E3Config (#85). The interop page said the limit was libe3's to fix, so that one RAN could not face Aerial and OCUDU at once. Agents with different configurations can run at the same time, each with its own ports or endpoints and ran_identifier, and the multi-RAN topology job in CI runs two of them. A RAN with peers on different links or encodings creates one agent for each, and that wiring belongs to the RAN application, not to the library. The page now says so, and that mixed links in one RAN have not been run because SCTP is off in CI. For E3-ResponseCode (#115) the page already asked OCUDU to close its enumeration. It now adds that if OCUDU needs a third code it can propose it on the page, and libe3 is open to adding the extension marker together with the code as one wire change, and to reading an unknown value as a refusal. The ledger gets a documentation row. No code, no grammar and no VERSION change. Assisted-by: Claude:claude-sonnet-5-5 Signed-off-by: Thecave3 <thecave003@gmail.com>
Thecave3
force-pushed
the
docs/111-control-answer
branch
from
November 11, 2026 02:04
36f90d4 to
0a27fb7
Compare
Thecave3
force-pushed
the
docs/85-115-positions
branch
from
November 11, 2026 02:04
e86c612 to
f6021c0
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The interop page said a libe3 RAN agent's one-link, one-encoding limit was libe3's to fix (#85). It now says that agents with different configurations can run at the same time, each with its own ports or endpoints and
ran_identifier, and that a RAN with Aerial and OCUDU peers creates one agent for each. That wiring belongs to the RAN application, not to the library. The multi-RAN topology job in CI runs two agents this way. Mixed links in one RAN have not been run, because SCTP is off in CI (#81).For
E3-ResponseCode(#115) the page already asked OCUDU to close its enumeration. It now adds that if OCUDU needs a third code it can propose it on the page, and libe3 is open to adding the extension marker together with the code as one wire change, and to reading an unknown value as a refusal.The ledger gets a documentation row.
What changes
Documentation only:
docs/interop.md. No code, no grammar, noVERSIONchange. #85 and #115 can close with no libe3 change once this merges.Stack
Based on #149, which also edits the interop page. Stack: #146, #147, #148, #149, this PR.